Skip to content

fix(deps): bump @octopusdeploy/api-client to 3.11.7 - #119

Open
zentron wants to merge 1 commit into
mainfrom
robe/bump-api-client-ai-agent
Open

zentron wants to merge 1 commit into
mainfrom
robe/bump-api-client-ai-agent

Conversation

@zentron

@zentron zentron commented Nov 22, 2026

Copy link
Copy Markdown

Background

api-client.ts#294, released in 3.11.7, adds AI coding agent detection to the User-Agent. Bumping here means requests from the MCP server identify the agent driving them.

Results

When an agent is detected, the User-Agent gains an (ai-agent=<Name>) comment at the very end:

ts-octopusdeploy octopus-mcp-server/2.3.3 (claude-code/2.1.42) (ai-agent=ClaudeCode)

The existing prefix is unchanged, so the server's ts-octopusdeploy octopus-mcp-server checks (the local MCP disabled setting and MCP usage telemetry) keep working. The lockfile also picks up api-client's own adm-zip 0.6.1 and axios floor bump.

Testing

npm run build and npm run lint pass, and all unit tests pass. The 11 failing tests are the integration tests that need a live Octopus instance, and they fail the same way on main.

Follow-up

The client now also accepts an aiAgent option. Passing the MCP clientInfo.name from the initialize handshake would identify the agent even when it doesn't export environment variables. That's left for a separate PR.


Generated by Claude Code

Picks up AI coding agent detection in the User-Agent
(OctopusDeploy/api-client.ts#294).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T4ijpGHFpAqBBMhn5WKUq2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant